2. Photomanager 128 or 64 (2.0 with search feature) (application)
3. Photo Db file (found here) (application data)
4 Photo Albums 1,2 and 3 samples (found here) (application data)
5. Scrap Peek 3.4 and/or Photo Mover (applications) found under Q-Link may be of use if you do not own geos Photo Manager 2.0 with search function. Also you can build us multiple photos in geofile as to your liking Then by using
@Retriver
(found under Q-link) you can automaticaly create your custom photo album for that special project.
@UNDERSTANDING:
By using geoFile in conjunction with Photomanager 128 or 64 2.0, one can increase the number of search fields greatly and thereby giving greater classification and organization to your Photo Albums which will in turn speed up your ability to find and use that proper photo.
@OPERATION:
On your disk or REU, place geoFile, PhotoManager 128 2.0, Photo Albums 1,2,3 and the Photo Db File. Open the Photo Db File. Here there will be 8 fields to classify or search for your photo. The Photo Db File is self explanatory or just common sense.
@DISK ID:
The number and letter you assign to each disk in your library.
@ALBUMN #:
The number of Albums you have on each disk in your library
@PAGE #:
The page number you assign to each photo in your library of Albums.
@CATAGORY:
The name you assign to your photo. Keep this simple and standard.
@CLASS:
A sub-title to help organize and search. Keep this simple and standard.
@DESCRIPTION:
A brief description of the photo. Here you could be more detailed.
@DATE USED:
This could be optional.
@RREFERENCE:
A tracking feature if you would like to link to other data files.
It is advisable to keep each
@Photo
@Db data file
on each
@ Photo Album (Disk) Library
that you classify. This will keep your sanity.
The design of the Photo Db data file and the Photo Albums were over-simplified for ease of understanding and of course you will want to alter this to meet your particular requirements. We hope this will be of use to some of you.
You might be more interested in developing this concept using the Textmanager 2.0.